home *** CD-ROM | disk | FTP | other *** search
- Path: news.netxpress.com!root
- From: ghporter@NetXpress.com (Glenn H. Porter)
- Newsgroups: comp.lang.c
- Subject: Re: Why does the "universal bugfunction" gets() survive in 1996?
- Date: Thu, 21 Mar 1996 14:18:37 GMT
- Organization: Digital Alpha Server NetXpress.com
- Message-ID: <4irokq$j1b@ferrari.NetXpress.com>
- References: <DoDGq8.Dqq@scn.org>
- NNTP-Posting-Host: ppp-1-18.netxpress.com
- X-Newsreader: Forte Free Agent 1.0.82
-
- kurt@scn.org (Kurt Cockrum) wrote:
-
- >especially since it's inherently dangerous and is potentially a grave disservice
- >to any user?
-
- >-- kurt@scn.org kurt@grogatch.seaslug.org (Kurt Cockrum)
- >Chair, Seattle-King County Save the Stupids Foundation
-
- Kurt,
-
- No function is inherently dangerous. The danger lies in expecting the
- compiler/language to keep you from doing something dangerous. My
- first C teacher told each of his classes "If you don't see the BIOS
- copyright message as your program output, you're not trying. Just
- make sure you don't see it twice for the same bug."
-
- If you use a function that dosn't check the length of the buffer, then
- you have to check the buffer. It's that simple. If you don't like
- it, don't use it.
-
- Regards,
- Glenn
-
-